This change is actually wrong. Originally it did indeed land as fs.promises. I would have kept it as is therefore. There should be another commit that changed it later on.

A good alternative would be to add the commit that changed it to fs/promises.

Feel free to do either, I simply relied on @devsnek's and others reviews.

But this isn't a commit message. This is a textual list of notable changes. Unless v10.0.0 shipped with fs.promises rather than fs/promises, this change is correct, IMO. Later on, when the commits are all listed, it says fs.promises and that is correct for the reason you identify here. But this section should not be true to specific commits but instead explain the notable change in the release.

This does raise an interesting question though, which is:

Is it necessary to list the commits with the notable changes?

Perhaps it is helpful in some ways, but perhaps it is also misleading. A notable change will often receive subsequent modifications after initially landing. We are not doing the end user favors by providing information in "Notable changes" that describes a change in a form that it was never actually released.

Might this entry in particular be better with no link to a commit and maybe a link to relevant docs about the feature instead?

People reading release notes rarely want to look at source changes, I imagine. Are we making the mistake of designing these release notes for us and not for the end user? Do we need Release Notes that are separate from the ChangeLog and the ChangeLog should be more dry listings and less text? (I don't know the answer here, and this is probably not the place to discuss it, but if someone wants to discuss this in the Release repo or discussion board, maybe that's good?)